System for software service upgrade

ABSTRACT

Examples are disclosed for upgrading services of a software-based service according to a predefined sequence to account for dependencies between services. An upgrade package that includes a manifest defining an order for upgrading services of the software-based system is retrieved. Each service is upgraded according to the sequence and a status log is modified following each upgrade to include a unified status summary associated with all services being upgraded.

BACKGROUND

Data centers include physical and virtual components that, whenexecuted, provide web services, cloud computing environments,virtualization environments, as well as other computing systems. Datacenters can include hardware and software to provide computervirtualization services, which relate to the creation of a virtualizedversion of a physical device, such as a server, a storage device, acentral processing unit (CPU), a graphics processing unit (GPU), orother computing resources.

Data centers can also include virtual machines (VMs), which includeemulations of a computer system that can be customized to include apredefined amount of random access memory (RAM), storage space, as wellas other computing resources that emulate a physical machine. Operatinga data center can involve maintaining hundreds to thousands of CPUs,GPUs, and other physical hardware, as well as corresponding software.The software can be provided by different third-party providers whichcan result in software upgrades and patches being available at differentrelease cycles. Due to dependencies that can be present between thedifferent types of software used within the computing infrastructure ofthe data center, upgrading the software without consideration of thedependencies can be problematic and cause complications.

BRIEF DESCRIPTION OF THE DRAWINGS

Many aspects of the present disclosure can be better understood withreference to the following drawings. The components in the drawings arenot necessarily to scale, with emphasis instead being placed uponclearly illustrating the principles of the disclosure. Moreover, in thedrawings, like reference numerals designate corresponding partsthroughout the several views.

FIG. 1 is a drawing of an example of a network infrastructure includingcomponents connected through a network including a management servicefor upgrading software components in a virtualized environment.

FIG. 2 is a drawing of an example manifest that defines an examplesequence for upgrading software components in the virtualizedenvironment.

FIG. 3 is a flowchart that illustrates functionality implemented bycomponents of the network environment of FIG. 1 .

DETAILED DESCRIPTION

The present disclosure relates to automating service upgrades within thecomputing infrastructure of a software-defined data center (SDDC) whileconsidering the interdependencies between the services. As upgrades andpatches become available for services and other types of applicationsinstalled on host devices within a data center, data center operatorscan request an upgrade of the installed services. However, due topossible dependencies between different services, complications canoccur if one of the services is upgraded prior to other services. Thesecomplications could result in inoperability of one or more of theservices which can affect the overall operation of the data center.Accordingly, performing automated upgrades of services based on apredetermined sequence that factors the interdependencies between theservices can reduce complications with service upgrades.

A software defined data center (SDDC) infrastructure can includedifferent software-based systems that are used for the overallimplementation and operation of a virtualized computing environment foran enterprise. The software-based systems can be created using genericthird-party software services in combination with native services.Patches and upgrades can become available for the different types ofsoftware services used to create the systems of the virtualizedcomputing environment. One implementation of the virtualized computingenvironment can include a life cycle manager that can manage thedeployment, upgrades, and configuration of the different software-basedsystems and services.

To simplify the deployment and upgrades of a software-based system andprovide a single unified process for upgrading the services, an upgradebundle can be generated. The upgrade bundle can define the individualservice upgrades associated with an overall upgrade of a software-basedsystem of the virtualized computing environment. When a system orportion of a system is to be upgraded, the upgrade bundle can include alist of service upgrades associated with the system upgrade.

The upgrade bundle can include a manifest that defines a sequence forexecuting the available service upgrades. A predefined sequence can bebased on a determination of an upgrade order given the differentinterdependencies between the services to be upgraded. For example, auser can review the updates and security issues for a third-partyservice upgrade release and determine if one service should be installedprior to another service. In one example, the user can identify that aversion associated with a first service is incompatible with a versionof a second service. Therefore, the user can determine that the firstservice should be upgraded before the second service to avoid theincompatibility issues associated with the different versions. Themanifest can be generated based on the determination of the upgradeorder.

The manifest can further identify a location of the executable codeassociated with the upgrade for each of the different services. Theservices can include third-party services, native services, or acombination of third-party and native services. Using the resourcesprovided in the manifest, an upgrade manager can sequentially executethe upgrades for each of the services based on the predefined sequence.As a result, the services can be upgraded automatically in an order thatprevents complications from interdependencies. In addition, the manifestis able to provide a centralized list and location of the differentservice upgrades that are associated with a software system upgrade andare provided by different service providers. This can provide asimplified process for version management as the versions of theservices to be upgraded can be associated with a given system upgrade.For example, the different versions of the services can be associatedwith a version of the software system that they are used to implement.

During the upgrade of the multiple services of a software-based system,a status log can be generated and updated to track the status of eachupgrade in a single unified view. The status log can provide statusinformation and any failure or error information associated with eachservice upgrade. As such, an administrator tracking the service updatesfor the different service upgrades can view the status and failureinformation in a single unified view instead of having to log in eachindividual service to track the status and view any corresponding errorsor failures.

Turning now to FIG. 1 , an example of a networked environment 100 isshown. The networked environment 100 can include a computing environment103 and computing systems 106 in communication with one another over anetwork 109. The network 109 can include, for example, the Internet,intranets, extranets, wide area networks (WANs), local area networks(LANs), wired networks, wireless networks, other suitable networks, orany combination of two or more such networks.

The networks of the networked environment 100 can include satellitenetworks, cable networks, Ethernet networks, telephony networks, andother types of networks. The computing systems 106 can include devicesinstalled in racks 112 which can make up a server bank, aggregatecomputing system, or a computer bank in a data center or other likefacility. In some examples, the computing systems 106 can includehigh-availability computing systems. A high-availability computingsystem is a group of computing devices that acts as a single system andprovides a continuous uptime. The devices in the computing systems 106can include any number of physical machines, virtual machines, virtualappliances, and software, such as operating systems, drivers,hypervisors, scripts, and applications.

The computing systems 106 and the hardware and software componentscontained therein can include infrastructure of the networkedenvironment 100 that can provide one or more computing services 114.Computing services 114 can include virtualization services. Forinstance, the computing services 114 can include those that servevirtual desktops to end users. Thus, the computing environment 103 canalso be described as a virtual desktop infrastructure (VDI) environmentin some examples. In other examples, the computing services 114 caninclude those that provide a public cloud computing environment, aprivate cloud computing environment, or a hybrid cloud computingenvironment (a combination of a public and private cloud computingenvironment). Therefore, the computing environment 103 can be referredto as a cloud computing environment in some examples. Further, thecomputing services 114 can include those that provide data to one ormore on-premise devices, which can include computing devices physicallylocated in the premises of an enterprise and communicating over anenterprise network having traffic diverted through a firewall. Thecomputing services 114 can include native services as well asthird-party services implemented by third-party service providers.

In some examples, the computing environment 103 can include anenterprise computing environment that includes hundreds or eventhousands of physical machines, virtual machines, and other softwareimplemented in devices stored in racks 112 (e.g., 112 a, 112 b),distributed geographically, and connected to one another through thenetwork 109. A virtual machine or virtual appliance is implemented usingat least one physical device, such as a server or other computingdevice.

The devices in the racks 112 can include computing resources. Thecomputing resources can include physical computing hardware, such asmemory and storage devices, switches 115 (e.g., 115 a . . . 115 d),hosts 118 (e.g., 118 a . . . 118 n), graphics cards, central processingunits (CPUs), power supplies, and similar devices. The devices, such ashosts and switches, can have dimensions suitable for quick installationin slots on the racks 112. In some examples, the hosts 118 can includerequisite physical hardware and software to create and managevirtualization infrastructure or a cloud computing environment. Also, insome examples, the computing resources can also include virtualcomputing resources, such as virtual machines or other software.

The hosts 118 can include a pre-configured hyper-converged computingdevice where a hyper-converged computing device includes pre-tested,pre-configured, and pre-integrated storage, server and networkcomponents, including software, that are positioned in an enclosureinstalled in a slot on a rack 112.

Each host 118 can include one or more virtual machines as well as ahypervisor. In some examples, the hypervisor can be installed on a host118 to support a virtual machine execution space within which one ormore virtual machines can be concurrently instantiated and executed.Additionally, the hypervisor can include the ESX hypervisor by VMWARE,the ESCI hypervisor by VMWARE, or similar hypervisor, in some examples.The computing systems 106 can be scalable, meaning that the computingsystems 106 in the networked environment 100 can increase or decreasedynamically to include or remove hosts 118, switches15, GPUs, powersources, and other components, without degrading performance of avirtualization or cloud computing environment.

One or more computing services 114 can be provided through execution ofan application or service on one or more of the virtual machines. Thecomputing services 114 can include, for example, web services in someexamples that can be invoked by submitting requests over the network 109for particular actions to be performed or for particular data to bereturned. Additionally, in some examples, the computing services 114 canbe implemented in computing containers. Each of the containers caninclude a self-contained execution environment having its own CPU,memory, block input/output (I/O), and network resources which areisolated from other containers. In some examples, a single one of thecontainers can implement a single one of the computing services 114.

The computing environment 103 can include a server or any other systemproviding computing capability. Alternatively, the computing environment103 can include one or more computing devices that are arranged, forexample, in one or more server banks, computer banks, computingclusters, or other arrangements. The computing environment 103 caninclude a grid computing resource or any other distributed computingarrangement. The computing devices can be located in a singleinstallation or can be distributed among many different geographicallocations. Although shown separately from the computing systems 106, itis understood that in some examples the computing environment 103 can beincluded as all or a part of the computing systems 106.

The computing environment 103 can include or be operated as one or morevirtualized computer instances in some examples. For purposes ofconvenience, the computing environment 103 is referred to in thesingular. As the computing environment 103 communicates with thecomputing systems 106 and client devices 116 over the network 109,sometimes remotely, the computing environment 103 can be described as aremote computing environment 103 in some examples. Additionally thecomputing environment 103 can be implemented in hosts 118 of a rack 112and can manage operations of a virtualized or cloud computingenvironment through interaction with the computing services 114.

The computing environment 103 can include a data store 121. The datastore 121 can include memory of the computing environment 103, massstorage resources of the computing environment 103, or any other storageresources on which data can be stored by the computing environment 103.The data store 121 can include memory of the hosts in the racks 112 insome examples. For instance, the data store 121 can include one or morerelational databases, such as structure query language (SQL) databases,non-SQL databases, or other relational or non-relational databases. Thedata stored in the data store 121, for example, can be associated withthe operation of the services or functional entities described below.

The data store 121 can include an upgrade bundle 124 and an upgradestatus log 127. The upgrade bundle 124 includes a bundle of upgrades andpatches for software services associated with a software-based system ofthe data center. The upgrade bundle 124 can include version data 130, amanifest 133, and upgrade executables 136. The version data 130 candefine a version associated with a particular system upgrade. Forexample, assume that an upgrade bundle 124 corresponds to an upgrade ofthe life cycle manager (LCM) 139. The version data 130 can identify theparticular version of the LCM 139 with respect to the particular upgradebundle 124. There can be multiple upgrade bundles associated withdifferent software-based systems of the data center and differentversions of the different systems.

The manifest 133 identifies the different upgrade elements 202 (FIG. 2 )that are available with respect to an upgrade of a software-based systemof the virtualized computing environment. Each upgrade element 202 cancorrespond to a service that has an available upgrade or patch. Theupgrade elements 202 can be listed in the manifest according to an orderin which each element is to be upgraded based on dependencies betweenthe different services. For each upgrade element 202, the manifest 133can include additional information including an executable handle 204(FIG. 2 ) identifying a location of the upgrade executable 136, anexecutable name, an executable type, executable parameters, status filelocation, status summaries, a timeout value, and version information.

The upgrade executable 136 corresponds to executable code used toupgrade the particular service. Although the upgrade executable 136 isshown as being included in the upgrade bundle 124, the upgradeexecutable 136 can be located at a remote location associated with athird-party service provider or can be located in the data store 121apart from the upgrade bundle 124. Regardless of the location of theupgrade executable 136, the executable handle 204 included in themanifest 133 can be used to call the upgrade executable 136 and initiateexecution of the service upgrade.

The upgrade status log 127 includes status data associated with each ofthe individual upgrades of the services. The upgrade status log 127 canbe modified with status summaries during each upgrade with respect tocompletion, status, error detection, or other types of statusinformation. In some examples, the third-party upgrade manager 142 orthe life cycle manager 139 can obtain status information from statusfiles created during the execution of a corresponding upgrade executable136. The third-party upgrade manager 142 or the life cycle manager 139can modify the upgrade status log 127 to include information obtainedfrom the respective status files. In some examples, the manifest 133includes predefined summaries that can be included in the upgrade statuslog 127 based the particular service upgrade. The upgrade status log 127can provide a single unified view for an administrator to review duringthe upgrade process thereby eliminating the need for the administratorto log into each service separately to initiate the upgrade and trackthe status upgrade.

The components executed on the computing environment 103 can include amanagement service 145, computing services 114, a management console 148as well as other applications, services, processes, systems, engines, orfunctionality not discussed in detail herein. The management service 145can oversee the operation of the networked environment 100 throughmanagement of the computing systems 106 as well as the physical andvirtual computing resources that make up the computing systems 106. Insome examples, an enterprise, organization, or other entity can operatethe management service 145 to oversee or manage the operation of devicesin the racks 112, such as servers, switches, GPUs, power supplies,cooling systems, and other components.

The physical and virtual components of the computing systems 106 canprocess workloads. Workloads can refer to the amount of processing thata server, switch, GPU, or other physical or virtual component has beeninstructed to process or route at a given time. The workloads can beassociated with virtual machines, public cloud services, private cloudservices, hybrid cloud services, virtualization services, devicemanagement services, or other software executing on the servers. Forinstance, the workloads can include tasks to be processed to provideemployees of an enterprise with remote desktop sessions or othervirtualized computing sessions.

The management service 145 can include a life cycle manager 139 and athird-party upgrade manager 142. The life cycle manager 139 can managethe deployment, upgrades, and configuration of the systems associatedwith the operation of the virtualized computing environment and thecomputing resources that make up the computing systems 106. A datacenter administrator or cloud computing operator can interact with thelife cycle manager 139 using the management console 148 accessible by aclient device 116 to schedule, initiate, and configure upgrades forsoftware systems associated with the operation of the virtualizedcomputing environment. The life cycle manager 139 can identify anddownload the appropriate upgrade bundles 124 for a requested systemupdate. In some examples, the life cycle manager 139 can select aparticular upgrade bundle 124 from a plurality of upgrade bundles 124according to the software system to be upgraded and a version associatedwith the requested system.

The third-party upgrade manager 142 can manage the upgrade ofthird-party services associated with the computing services 114 or othersoftware-based systems of the networked environment 100. The third-partyupgrade manager 142 can interact with the life cycle manager 139 tomanage the upgrades associated with different third-party services. Forexample, the third-party upgrade manager 142 can unpack the upgradebundle 124 obtained by the life cycle manager 139 and initiate theupgrades of third-party services according to the predefined sequencewithin the manifest 133. In some examples, as shown in FIG. 1 , thethird-party upgrade manager 142 is a plug-in or other type of standaloneapplication. In other examples, the third-party upgrade manager 142 canbe integrated within the life cycle manager 139 such that thethird-party upgrade manager 142 is a component of the life cycle manager139.

The management console 148 can provide an administrative interface forconfiguring the operation of individual components in the networkedenvironment 100. For instance, the management console 148 can provide anadministrative interface for the management service 145. As an example,the management console 148 can provide a user interface to allow notifyan administrative user of available upgrades associated with computingservices or resources of the networked environment 100. The managementconsole 148 can also provide a user interface to allow theadministrative user to request upgrades and view the status associatedwith the requested upgrades. Accordingly, the management console 148 cancorrespond to a web page or a web application provided by a web serverhosted in the computing environment 103. In other implementations,however, the management console 148 can be implemented as a dedicated orstandalone application.

Turning now to FIG. 2 , shown is an example manifest 133 that can beincluded in an upgrade bundle 124 and used by the third-party upgrademanager 142 or the life cycle manager 139 when updating the third-partyservices used in the implementation of and operation of a data center.The manifest 133 provides a centralized list of third-party upgradesassociated with a particular system upgrade. In some examples, themanifest 133 can be generated by a user tasked with identifyingdependencies associated with different services and versions ofservices. Another benefit of the manifest 133 is that the differentversions of services can be managed and mapped to a single version ofthe overall system that implements the services.

As shown in FIG. 2 , the manifest 133 identifies a manifest version andthe different upgrade elements 202 (e.g., 202 a, 202 b, 202 c) to beupdated with respect to the manifest version. The manifest 133 lists theupgrade elements 202 in the order in which they are to be executed. Forexample, in the manifest of FIG. 2 , upgrade element 202 a will beexecuted before upgrade element 202 b and 202 c.

For each upgrade element 202, the manifest can include an executablehandle 204 (e.g., 204 a, 204 b, 204 c), an executable name, anexecutable type, executable parameters, a status file location, statussummaries, a timeout value, and other information. The executable handle204 corresponds to a location of where the executable code for theupgrade can be found. In some examples, the executable code can be localto the computing environment 103. In other examples, the executable codecan be stored in a remote location that is accessible over the network109. For example, the executable code can be obtained from a third-partyservice provider associated with the given upgrade. The executable namecorresponds to a name associated with the given upgrade. The executabletype can define the type of executable associated with the upgrade. Forexample, the executable type for each of the upgrade elements 202 isPYTHON. However, the executable type can vary as can be appreciated.Other features that can be included in the manifest can include a statusfile location which defines a location of a status file associated withthe execution of the upgrade executable 136 for the given upgradeelement 202. The third-party upgrade manager 142 or the life cyclemanager 139 can determine the status associated with the given upgradeby accessing the status file associated with the execution of thethird-party upgrade executable 136 for the given upgrade element 202.Therefore, the third-party upgrade manager 142 or the life cycle manager139 can use the location provided in the manifest 133 to determine thecurrent upgrade status and modify the upgrade status log 127 accordingto the status obtained from the respective status file.

Another feature that can be included in the manifest 133 is a timeoutvalue. The timeout value can correspond to a maximum amount of time fora particular upgrade. The third-party upgrade manager 142 or the lifecycle manager 139 tracks the amount of time that has lapsed since thestart of the execution of a particular upgrade. If an upgrade timeexceeds the timeout value, the third-party upgrade manager 142 or thelife cycle manager 139 can halt the overall upgrade and generate anerror message. The error message can signify that the upgrade failed dueto the timeout.

In some examples, the manifest 133 can include a user-defined summaryassociated with the upgrade. For example, the summary associated withupgrade element 202 b states that “Upgrading base OS rpms as part of LCMself-upgrade.” The third-party upgrade manager 142 or the life cyclemanager 139 can include this summary in the upgrade status log 127 thatis provided to an administrator and notifies the administrator whichcomponents are being updated.

Moving on to FIG. 3 , shown is a flowchart 300 that provides one exampleof the operation of a portion of the network environment 100. Theflowchart of FIG. 3 can be viewed as depicting an example of elements ofa method implemented by the management service management service 145,life cycle manager 139, third-party upgrade manager 142, or othercomponents executing in the computing environment 103. The separation orsegmentation of functionality as discussed herein is presented forillustrative purposes only.

Beginning with step 303, the life cycle manager 139 can obtain a requestfor an upgrade of a software-based system of virtualized computingenvironments from an administrator or other cloud computing operator.The request can be obtained from the management console 148 that isaccessed by a user. In some examples, the user can interact with themanagement service 145 using the management console 148 to manage andbuild a virtualized cloud computing environment for an enterprise.Through interactions with the life cycle manager 139, the administratorcan be notified of upgrades that are available with respect to differentsoftware systems of the virtualized environment managed by themanagement service 145. Using the management console 148, theadministrator can then request an upgrade of a particular system orportion of the system, and the request is received by the life cyclemanager 139.

At step 306, the life cycle manager 139 can retrieve the upgrade bundle124 associated with the requested upgrade from the data store 121. Insome examples, the life cycle manager 139 can determine the version ofthe system to be upgraded and can select the appropriate upgrade bundle124 from a plurality of upgrade bundles 124 based on the version. Forexample, if the currently installed version of the product is 2.0, thelife cycle manager 139 can determine that the requested upgrade versionis 2.1. In some examples, the request can include the version associatedwith the requested upgrade.

At step 309, the life cycle manager 139 can initiate the third-partyservice upgrades. In some examples, the life cycle manager 139 canprovide the third-party upgrade manager 142 with the upgrade bundle 124,and the third-party upgrade manager 142 can unpack the bundle to allowaccess to the different files, executable files, status logs, themanifest 133, and other information included in the bundle. The manifest133 can be specific to the third-party service upgrades associated withdifferent third-party service providers. The third-party upgrade manager142 can also create an upgrade status log 127 that is associated withthe given upgrade.

At step 312, the third-party upgrade manager 142 or the life cyclemanager 139 can identify the manifest 133 included in the upgrade bundle124. The manifest 133 includes an identification of the service upgradesassociated with the requested upgrade.

At step 315, the third-party upgrade manager 142 or the life cyclemanager 139 identifies a service to be upgraded in the manifest 133. Thethird-party upgrade manager 142 or the life cycle manager 139 can parsethe manifest to identify the different upgrade elements 202 thatcorrespond with the different services. As the manifest 133 provides asequence in which the different services are to be upgraded, thethird-party upgrade manager 142 or the life cycle manager 139 caninitially identity the first upgrade element 202 in the predefinedsequence.

At step 318, the third-party upgrade manager 142 or the life cyclemanager 139 executes a service upgrade associated with the identifiedservice. To execute the service upgrade, the third-party upgrade manager142 or the life cycle manager 139 identifies the executable handle 204of the upgrade element 202 corresponding to the identified service. Thethird-party upgrade manager 142 or the life cycle manager 139 can send acall using the executable handle 204 to execute the correspondingupgrade executable 136.

At step 321, the third-party upgrade manager 142 or the life cyclemanager 139 determines whether the upgrade is complete. The manifest 133can include a location of a status file created by the third-partyupgrade executable 136 upon being executed. The third-party upgrademanager 142 or the life cycle manager 139 can access the status filebased on the location provided in the manifest 133 to determine thestatus of the given upgrade. If the status file indicates that theupgrade is complete, the third-party upgrade manager 142 or the lifecycle manager 139 proceeds to step 324.

In step 324, third-party upgrade manager 142 or the life cycle manager139 determines if there is another upgrade to complete. For example, ifthere are other upgrades listed in the manifest 133 that have not beenexecuted, the third-party upgrade manager 142 or the life cycle manager139 will determine that there is another upgrade to execute and willreturn to step 315 to identify the next upgrade to execute according tothe predefined sequence. If there are no other upgrades to complete, thethird-party upgrade manager 142 or the life cycle manager 139 willproceed to step 330.

Returning to step 321, if the third-party upgrade manager 142 or thelife cycle manager 139 determines that the upgrade is not complete, thethird-party upgrade manager 142 or the life cycle manager 139 proceedsto step 327.

At step 327, the third-party upgrade manager 142 or the life cyclemanager 139 determines whether a timeout has occurred with respect tothe particular service upgrade. For example, the third-party upgrademanager 142 or the life cycle manager 139 can compare an amount of timeelapsed from the start of the given service upgrade with the timeoutvalue provided in the manifest 133. If the amount of time elapsedexceeds the timeout value, the third-party upgrade manager 142 or thelife cycle manager 139 proceeds to step 330. Otherwise, the third-partyupgrade manager 142 or the life cycle manager 139 returns to step 321.

At step 330, the third-party upgrade manager 142 or the life cyclemanager 139 modifies the upgrade status log 127. If there has been atimeout associated with the upgrade, third-party upgrade manager 142 orthe life cycle manager 139 modifies the upgrade status log 127 toinclude an error message associated with the upgrade. The error messagecan indicate that the upgrade for a given service did not complete inthe expected time. If all of the upgrades have been completed, thethird-party upgrade manager 142 or the life cycle manager 139 can modifythe upgrade status log 127 to indicate the completion of the serviceupgrades. Although FIG. 3 illustrates the upgrade status log 127 beingmodified at the completion of all of the upgrades, the upgrade statuslog 127 can be modified upon the completion of each upgrade listed inthe manifest 133. Upon updating the status log 127 to indicatecompletion of the service upgrades or an error associated with theservice upgrades, the process can proceed to completion.

Stored in the memory device are both data and several components thatare executable by the processor. Also stored in the memory can be a datastore and other data. A number of software components are stored in thememory and executable by a processor. In this respect, the term“executable” means a program file that is in a form that can ultimatelybe run by the processor. Examples of executable programs can be, forexample, a compiled program that can be translated into machine code ina format that can be loaded into a random access portion of one or moreof the memory devices and run by the processor, code that can beexpressed in a format such as object code that is capable of beingloaded into a random access portion of the one or more memory devicesand executed by the processor, or code that can be interpreted byanother executable program to generate instructions in a random accessportion of the memory devices to be executed by the processor. Anexecutable program can be stored in any portion or component of thememory devices including, for example, random access memory (RAM),read-only memory (ROM), hard drive, solid-state drive, USB flash drive,memory card, optical disc such as compact disc (CD) or digital versatiledisc (DVD), floppy disk, magnetic tape, or other memory components.

Memory can include both volatile and nonvolatile memory and data storagecomponents. In addition, a processor can represent multiple processorsand/or multiple processor cores, and the one or more memory devices canrepresent multiple memories that operate in parallel processingcircuits, respectively. Memory devices can also represent a combinationof storage devices, such as RAM, mass storage devices, flash memory, orhard disk storage. In such a case, a local interface can be anappropriate network that facilitates communication between any two ofthe multiple processors or between any processor and any of the memorydevices. The local interface can include additional systems designed tocoordinate this communication, including, for example, performing loadbalancing. The processor can be of electrical or of some other availableconstruction.

Client devices can be used to access user interfaces generated toconfigure or otherwise interact with the management service 145. Theseclient devices can include a display upon which a user interfacegenerated by a client application for providing a virtual desktopsession (or other session) can be rendered. In some examples, the userinterface can be generated using user interface data provided by thecomputing environment 103. The client device can also include one ormore input/output devices that can include, for example, a capacitivetouchscreen or other type of touch input device, fingerprint reader, orkeyboard.

Although the management service 145 and other systems described hereincan be embodied in software or code executed by general-purpose hardwareas discussed above, as an alternative, the same can also be embodied indedicated hardware or a combination of software/general purpose hardwareand dedicated hardware. If embodied in dedicated hardware, each can beimplemented as a circuit or state machine that employs any one of or acombination of a number of technologies. These technologies can includediscrete logic circuits having logic gates for implementing logicfunctions upon an application of one or more data signals, applicationspecific integrated circuits (ASICs) having appropriate logic gates,field-programmable gate arrays (FPGAs), or other components.

The flowcharts show an example of the functionality and operation of animplementation of portions of components described herein. If embodiedin software, each block can represent a module, segment, or portion ofcode that can include program instructions to implement the specifiedlogical function(s). The program instructions can be embodied in theform of source code that can include human-readable statements writtenin a programming language or machine code that can include numericalinstructions recognizable by a suitable execution system such as aprocessor in a computer system or other system. The machine code can beconverted from the source code. If embodied in hardware, each block canrepresent a circuit or a number of interconnected circuits to implementthe specified logical function(s).

Although the flowcharts show a specific order of execution, it isunderstood that the order of execution can differ from that which isdepicted. For example, the order of execution of two or more blocks canbe scrambled relative to the order shown. In addition, two or moreblocks shown in succession can be executed concurrently or with partialconcurrence. Further, in some examples, one or more of the blocks shownin the drawings can be skipped or omitted.

Also, any logic or application described herein that includes softwareor code can be embodied in any non-transitory computer-readable mediumfor use by or in connection with an instruction execution system suchas, for example, a processor in a computer system or other system. Inthis sense, the logic can include, for example, statements includingprogram code, instructions, and declarations that can be fetched fromthe computer-readable medium and executed by the instruction executionsystem. In the context of the present disclosure, a “computer-readablemedium” can be any medium that can contain, store, or maintain the logicor application described herein for use by or in connection with theinstruction execution system.

The computer-readable medium can include any one of many physical media,such as magnetic, optical, or semiconductor media. More specificexamples of a suitable computer-readable medium include solid-statedrives or flash memory. Further, any logic or application describedherein can be implemented and structured in a variety of ways. Forexample, one or more applications can be implemented as modules orcomponents of a single application. Further, one or more applicationsdescribed herein can be executed in shared or separate computing devicesor a combination thereof. For example, a plurality of the applicationsdescribed herein can execute in the same computing device, or inmultiple computing devices.

It is emphasized that the above-described examples of the presentdisclosure are merely possible examples of implementations set forth fora clear understanding of the principles of the disclosure. Manyvariations and modifications can be made to the above-describedembodiments without departing substantially from the spirit andprinciples of the disclosure. All such modifications and variations areintended to be included herein within the scope of this disclosure.

Therefore, the following is claimed:
 1. A system, comprising: at leastone computing device; at least one application executable by the atleast one computing device, wherein, when executed, the at least oneapplication causes the at least one computing device to at least:retrieve an upgrade package for upgrading a software-based system;identify a manifest within the upgrade package, the manifest defining aplurality of services included in the software-based system to upgradeand a predefined sequence for which individual services of the pluralityof services are to be upgraded to account for dependencies between theplurality of services; generate a status log associated with upgradingthe software-based system, the status log being generated to include aunified status summary associated with all of the services; and for theindividual services and in accordance to the predefined sequence:execute a respective service upgrade; determine a status of therespective service upgrade; and modify the status log to include thestatus of the respective service upgrade.
 2. The system of claim 1,wherein the individuals services correspond to a respective upgradeelement in a list of upgrade elements included in the manifest, theupgrade elements being listed in the list of upgrade elements accordingto the predefined sequence.
 3. The system of claim 2, wherein individualupgrade elements in the list of upgrade elements include at least one ofa location of executable code, an executable name, an executable type, atimeout value, or version information.
 4. The system of claim 1, whereindetermining the status of the respective service upgrade furthercomprises determining whether an amount of time executing the respectiveservice upgrade exceeds a maximum upgrade time defined in the manifestfor the respective service upgrade.
 5. The system of claim 4, wherein,when executed, the at least one application further causes the at leastone computing device to at least halt the upgrade of the software-basedsystem in response to determining the amount of time executing therespective service upgrade exceeds the maximum upgrade time, the statuslog being modified to include an error message to indicate an error inthe respective service upgrade.
 6. The system of claim 1, wherein, whenexecuted, the at least one application further causes the at least onecomputing device to select the upgrade package from a plurality ofupgrade bundle based at least in part on the software-based system to beupgraded and a version associated with the software-based system.
 7. Thesystem of claim 1, wherein the plurality of services comprises at leastone native service and at least one third-party service.
 8. Anon-transitory computer-readable medium embodying executableinstructions, which, when executed by a processor, cause at least onecomputing device to at least: retrieve an upgrade package for upgradinga software-based system; identify a manifest within the upgrade package,the manifest defining a plurality of services included in thesoftware-based system to upgrade and a predefined sequence for whichindividual services of the plurality of services are to be upgraded toaccount for dependencies between the plurality of services; generate astatus log associated with upgrading the software-based system, thestatus log being generated to include a unified status summaryassociated with all of the services; and for the individual services andin accordance to the predefined sequence: execute a respective serviceupgrade; determine a status of the respective service upgrade; andmodify the status log to include the status of the respective serviceupgrade.
 9. The non-transitory computer-readable medium of claim 8,wherein the individuals services correspond to a respective upgradeelement in a list of upgrade elements included in the manifest, theupgrade elements being listed in the list of upgrade elements accordingto the predefined sequence.
 10. The non-transitory computer-readablemedium of claim 9, wherein individual upgrade elements in the list ofupgrade elements include at least one of a location of executable code,an executable name, an executable type, a timeout value, or versioninformation.
 11. The non-transitory computer-readable medium of claim 8,wherein determining the status of the respective service upgrade furthercomprises determining whether an amount of time executing the respectiveservice upgrade exceeds a maximum upgrade time defined in the manifestfor the respective service upgrade.
 12. The non-transitorycomputer-readable medium of claim 11, wherein when executed, theexecutable instructions further cause the at least one computing deviceto at least halt the upgrade of the software-based system in response todetermining the amount of time executing the respective service upgradeexceeds the maximum upgrade time, the status log being modified toinclude an error message to indicate an error in the respective serviceupgrade.
 13. The non-transitory computer-readable medium of claim 8,wherein ,when executed, the executable instructions further cause the atleast one computing device to at least select the upgrade package from aplurality of upgrade bundle based at least in part on the software-basedsystem to be upgraded and a version associated with the software-basedsystem.
 14. A computer-implemented method, comprising: retrieving, by atleast one computing device, an upgrade package for upgrading asoftware-based system; identifying, by the at least one computingdevice, a manifest within the upgrade package, the manifest defining aplurality of services included in the software-based system to upgradeand a predefined sequence for which individual services of the pluralityof services are to be upgraded to account for dependencies between theplurality of services; generating, by the at least one computing device,a status log associated with upgrading the software-based system, thestatus log being generated to include a unified status summaryassociated with all of the services; and for the individual services andin accordance to the predefined sequence: executing, by the at least onecomputing device, a respective service upgrade; determining, by the atleast one computing device, a status of the respective service upgrade;and modifying, by the at least one computing device, the status log toinclude the status of the respective service upgrade.
 15. Thecomputer-implemented method of claim 14, wherein the individualsservices correspond to a respective upgrade element in a list of upgradeelements included in the manifest, the upgrade elements being listed inthe list of upgrade elements according to the predefined sequence. 16.The computer-implemented method of claim 15, wherein individual upgradeelements in the list of upgrade elements include at least one of alocation of executable code, an executable name, an executable type, atimeout value, or version information.
 17. The computer-implementedmethod of claim 14, wherein determining the status of the respectiveservice upgrade further comprises determining whether an amount of timeexecuting the respective service upgrade exceeds a maximum upgrade timedefined in the manifest for the respective service upgrade.
 18. Thecomputer-implemented method of claim 17, further comprising halting theupgrade of the software-based system in response to determining theamount of time executing the respective service upgrade exceeds themaximum upgrade time, the status log being modified to include an errormessage to indicate an error in the respective service upgrade.
 19. Thecomputer-implemented method of claim 14, further comprising selectingthe upgrade package from a plurality of upgrade bundle based at least inpart on the software-based system to be upgraded and a versionassociated with the software-based system.
 20. The computer-implementedmethod of claim 14, wherein the plurality of services comprises at leastone native service and at least one third-party service.